Repository navigation
chore(fullsend): remove customized scaffold, bump to v0.43.0, trim roles - #968
Conversation
The customized/ directory held only .gitkeep placeholders from the original fullsend-0.32.0 per-repo scaffold and is unused. The active Jira integration relies on .fullsend/config.yaml plus the harness/ and policies/ overrides, none of which reference customized/. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Update all fullsend version pins to v0.43.0, matching the hashes used in openshift/ocm-agent-operator: - fullsend.yaml / fullsend-poll-jira.yml: reusable-dispatch.yml pinned to d5f36921ac754705619f38c637ef692873809fbc (# v0.43.0). - fullsend-poll-jira.yml: fullsend binary release download v0.38.0 -> v0.43.0. - harness/code.yaml, harness/triage.yaml: agents base pinned to 7ab05564b3c9c0ab20197e0c8572b5905ffd75ca with refreshed sha256 digests. Repo-specific values (repository gate, ROSAENG JQL, master target branch) are left unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The review, retro, and prioritize roles are not used by this repo's Jira integration (no review/retro/prioritize agents are registered in the agents: section). Keep only the triage, coder, and fix roles. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (15)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 10 remain after this review. WalkthroughChangesFullsend now uses roles Fullsend updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Merge Risk: ⚪ Minimal · up to No concrete merge-blocking regression from these version and role updates was established. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@samanthajayasinghe: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RaphaelBut, samanthajayasinghe The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
🤖 Finished Retro · ✅ Success · Started 11:20 AM UTC · Completed 11:29 AM UTC Commit: Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.43 |
Retro: PR #968 — fullsend housekeeping bumpPR #968 was a clean housekeeping PR by Finding: stale version comments in harness configsThe PR updated the SHA pins in Evidence for existing issues (no new proposals needed)
Proposals filed
|
Summary
Housekeeping on the fullsend per-repo integration: drops unused scaffold, upgrades to the latest fullsend release, and trims roles to what this repo's Jira integration actually uses. Version pins mirror
openshift/ocm-agent-operator(v0.43.0). Modeled on openshift-online/rosa-cora-agent#151.Commits
1. Remove empty
.fullsend/customized/scaffold folderThe
customized/directory held only.gitkeepplaceholders from the originalfullsend-0.32.0per-repo scaffold and was never used. The active Jira integration relies on.fullsend/config.yamlplus theharness/andpolicies/overrides, none of which referencecustomized/.2. Bump fullsend to v0.43.0
Update all fullsend version pins to v0.43.0, using the exact hashes from
openshift/ocm-agent-operator:.github/workflows/fullsend.yamlreusable-dispatch.yml@2db46c4…(v0.38.0) →@d5f36921…(v0.43.0).github/workflows/fullsend-poll-jira.ymlgh release downloadv0.38.0→v0.43.0.github/workflows/fullsend-poll-jira.ymlreusable-dispatch.yml@2db46c4…(v0.38.0) →@d5f36921…(v0.43.0).fullsend/harness/code.yamlbase@48511880…→@7ab05564…(refreshed sha256).fullsend/harness/triage.yamlbase@48511880…→@7ab05564…(refreshed sha256)Verified the v0.43.0
reusable-dispatch.ymlsignature (required inputsmint_url,gcp_region; required secretFULLSEND_GCP_PROJECT_ID) is backward-compatible with the existing shim. Repo-specific values (repository gate, ROSAENG JQL,mastertarget branch) are left unchanged.3. Remove
review,retro, andprioritizeroles from fullsend configThese roles are not used by this repo's Jira integration (no
review/retro/prioritizeagents are registered in theagents:section). Roles are nowtriage,coder,fix, matching the registeredtriageandcodeagents. (osdctl carried aprioritizerole in addition to thereview/retroremoved in the reference PR; it is dropped here for the same reason.)Testing
yq).customized/or old version pins.🤖 Generated with Claude Code
Summary by CodeRabbit